feat(spanner): add Client Context support to options by aseering · Pull Request #1499 · googleapis/python-spanner

aseering · 2026-02-24T18:01:22Z

Re-opening #1495 due to permissions issues.

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
Ensure the tests and linter pass
Code coverage does not decrease (if any source code was changed)
Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

This change adds support for ClientContext in Options and ensures it is propagated to ExecuteSql, Read, Commit, and BeginTransaction requests. It aligns with go/spanner-client-scoped-session-state design. ClientContext allows passing opaque, RPC-scoped side-channel information (like application-level user context) to Spanner. This implementation supports setting ClientContext at the Client, Database, and Request levels, with request-level options taking precedence. Key changes: - Added ClientContext to types/spanner.py and exposed it. - Updated Client.__init__ to accept a default client_context. - Added helpers for merging ClientContext with correct precedence. - Updated Snapshot, Transaction, Batch, and Database wrappers to propagate the context. - Added comprehensive unit tests in tests/unit/test_client_context.py.

- Update Session.transaction to accept client_context. - Update unit tests to support client_context propagation. - Update mock objects in tests to match the expected attribute hierarchy. - Clean up nested imports in test files.

Implement a double-checked locking pattern in Transaction and _SnapshotBase methods. When multiple threads attempt to use a lazy transaction simultaneously, they race to acquire the lock. Previously, losing threads would acquire the lock and blindly send another 'begin transaction' request, ignoring that the winner had already initialized the transaction ID. This change ensures that threads re-check self._transaction_id after acquiring the lock. If the ID is present, they skip the initialization request and use the established ID.

- Fix critical security vulnerability in where in-place modification of the base object could lead to context leakage across requests. - Replace with throughout , , , and for better robustness and subclass support. - Simplify construction logic in for better readability. Based on suggestions from Gemini Code Assist.

…upport

gemini-code-assist · 2026-02-24T18:01:55Z

Summary of Changes

Hello @aseering, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive support for ClientContext across the Google Cloud Spanner Python client library. This enhancement allows users to define and propagate client-specific contextual information, such as secure context parameters, throughout their Spanner interactions. The changes involve defining a new ClientContext type, implementing robust merging logic for these contexts, and integrating this functionality into the core client, database, session, batch, snapshot, and transaction classes. This provides greater flexibility and control over contextual data associated with Spanner API calls.

Highlights

New ClientContext Type: Introduced a new ClientContext message type in google.cloud.spanner_v1.types.spanner.py to allow attaching client-owned context, such as secure context parameters, to requests.
ClientContext Merging Logic: Added helper functions _merge_client_context and _merge_request_options in google/cloud/spanner_v1/_helpers.py to handle the merging of ClientContext and RequestOptions objects, ensuring higher precedence contexts overwrite base fields.
Client-Level ClientContext Support: The Client class constructor in google/cloud/spanner_v1/client.py now accepts an optional client_context parameter, allowing a default context to be set for all requests made by the client.
Propagation Across Operations: Integrated client_context support into various Spanner operations, including batch writes, transactions, snapshots, and SQL execution, by updating relevant classes (_BatchBase, MutationGroups, _SnapshotBase, Transaction) and methods (database.batch, database.mutation_groups, database.batch_snapshot, database.run_in_transaction, session.transaction, session.run_in_transaction).
Improved Type Checking: Replaced direct type comparisons (type(var) is dict) with isinstance(var, dict) for more robust type checking in _helpers.py.
Unit Test Coverage: Added a new dedicated unit test file tests/unit/test_client_context.py to thoroughly verify the functionality and propagation of ClientContext.

Changelog

google/cloud/spanner_v1/init.py
- Imported ClientContext from types.spanner.
- Added ClientContext to the module's __all__ export list.
google/cloud/spanner_v1/_helpers.py
- Imported ClientContext and RequestOptions types.
- Replaced type(combined) is dict with isinstance(combined, dict) in _merge_query_options.
- Added _merge_client_context function to merge two ClientContext objects.
- Added _merge_request_options function to merge ClientContext into RequestOptions.
google/cloud/spanner_v1/batch.py
- Imported _merge_client_context and _merge_request_options.
- Imported ClientContext type.
- Added client_context parameter to _BatchBase constructor and stored it.
- Added client_context parameter to MutationGroups constructor and stored it.
- Modified commit method to merge client and batch client_context into request_options.
- Modified batch_write method to merge client and mutation group client_context into request_options.
google/cloud/spanner_v1/client.py
- Imported ClientContext type.
- Added client_context parameter to the Client constructor.
- Stored the provided client_context in self._client_context after type validation.
google/cloud/spanner_v1/database.py
- Updated docstring for snapshot to mention client_context.
- Added client_context parameter to batch method.
- Updated docstring for batch to include client_context.
- Passed client_context to BatchCheckout in batch method.
- Added client_context parameter to mutation_groups method.
- Updated docstring for mutation_groups to include client_context.
- Passed client_context to MutationGroupsCheckout in mutation_groups method.
- Added client_context parameter to batch_snapshot method.
- Updated docstring for batch_snapshot to include client_context.
- Passed client_context to BatchSnapshot in batch_snapshot method.
- Updated docstring for run_in_transaction to include client_context.
- Added client_context parameter to BatchCheckout constructor and stored it.
- Passed client_context to Batch constructor in BatchCheckout.__enter__.
- Added client_context parameter to MutationGroupsCheckout constructor and stored it.
- Passed client_context to MutationGroups constructor in MutationGroupsCheckout.__enter__.
- Added client_context parameter to BatchSnapshot constructor and stored it.
- Passed client_context to Snapshot constructor in BatchSnapshot._get_snapshot.
google/cloud/spanner_v1/session.py
- Added client_context parameter to transaction method.
- Updated docstring for transaction to include client_context.
- Passed client_context to Transaction constructor in transaction method.
- Updated docstring for run_in_transaction to include client_context.
- Popped client_context from kw in run_in_transaction.
- Passed client_context to Transaction constructor in run_in_transaction loop.
google/cloud/spanner_v1/snapshot.py
- Imported _merge_client_context and _merge_request_options.
- Imported ClientContext type.
- Added client_context parameter to _SnapshotBase constructor and stored it.
- Modified read method to merge client and snapshot client_context into request_options.
- Modified execute_sql method to merge client and snapshot client_context into request_options.
- Modified _begin_transaction method to merge client and snapshot client_context into request_options.
- Added client_context parameter to Snapshot constructor and passed it to super.
google/cloud/spanner_v1/transaction.py
- Imported _merge_client_context and _merge_request_options.
- Added client_context parameter to Transaction constructor and passed it to super.
- Modified commit method to merge client and transaction client_context into request_options.
- Modified execute_update method to merge client and transaction client_context into request_options.
- Modified batch_update method to merge client and transaction client_context into request_options.
google/cloud/spanner_v1/types/init.py
- Imported ClientContext from spanner.
- Added ClientContext to the module's __all__ export list.
google/cloud/spanner_v1/types/spanner.py
- Added ClientContext to the RequestOptions message.
- Defined the new ClientContext message type with a secure_context map field.
tests/unit/spanner_dbapi/test_connection.py
- Initialized self._client_context = None in _Client.__init__.
tests/unit/test_backup.py
- Initialized self._client_context = None in _Client.__init__.
tests/unit/test_batch.py
- Initialized self._instance._client._client_context = None in _Database.__init__ mock.
tests/unit/test_client_context.py
- Added new test cases for _merge_client_context and _merge_request_options.
- Added tests for Client initialization with client_context.
- Added tests for client_context propagation in Snapshot.execute_sql, Transaction.commit, Transaction.execute_update, MutationGroups.batch_write, BatchSnapshot, and Database.snapshot.
- Added a test to confirm client_context is not supported in Transaction.rollback.
tests/unit/test_database.py
- Imported ExecuteSqlRequest.
- Initialized self._client_context = None in _Client.__init__ mock.
- Initialized instance._client._client_context = None in _Database.__init__ mock.
tests/unit/test_instance.py
- Initialized self._client_context = None in _Client.__init__ mock.
tests/unit/test_pool.py
- Cleaned up redundant imports.
- Initialized self._instance._client._client_context = None in _Database mock for session creation.
tests/unit/test_session.py
- Initialized database._instance._client._client_context = None in _make_database mock.
tests/unit/test_snapshot.py
- Initialized self._client_context = None in _Client.__init__ mock.
tests/unit/test_spanner.py
- Initialized self._client_context = None in _Client.__init__ mock.
tests/unit/test_transaction.py
- Initialized self._client_context = None in _Client.__init__ mock.

Activity

The pull request is a re-opening of a previous attempt (feat(spanner): add ClientContext support to options #1495) to implement this feature, which was closed due to permissions issues.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request effectively adds support for ClientContext across the Spanner client library, allowing for more granular control over request options. The changes are consistently applied through various layers of the API, from the client down to individual transactions and snapshots. The addition of a comprehensive test suite for the new functionality is also a great inclusion. I have one suggestion to improve maintainability by refactoring a duplicated block of code into a shared helper function.

gemini-code-assist · 2026-02-24T18:08:06Z

google/cloud/spanner_v1/batch.py

+        if client_context is not None:
+            if isinstance(client_context, dict):
+                client_context = ClientContext(client_context)
+            elif not isinstance(client_context, ClientContext):
+                raise TypeError("client_context must be a ClientContext or a dict")
+        self._client_context = client_context


This block of code for validating and converting client_context is duplicated in several places (e.g., _BatchBase, MutationGroups, Client, _SnapshotBase). To improve maintainability and reduce code duplication, consider extracting this logic into a helper function in google/cloud/spanner_v1/_helpers.py.

…upport

chalmerlowe · 2026-03-02T15:12:18Z

📢 Migration Notice: 📢 This library is moving to the google-cloud-python monorepo soon.

We kept this PR open due to recent activity. We would like to finalize this PR so it can be merged if it is critical.

If we don't hear from the PR author, we will close this PR in the next few days. The PR can then be re-opened in the monorepo once the migration is complete and work can continue there.

olavloite · 2026-03-03T14:30:38Z

The test failures in this PR are not different from the failures in #1510, indicating that this PR is not introducing any new problems.

PR created by the Librarian CLI to generate Cloud Client Libraries code from protos. BEGIN_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `routing_hint` in messages `.google.spanner.v1.ResultSet` and `.google.spanner.v1.PartialResultSet` are changed PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment in message `.google.spanner.v1.TransactionOptions.ReadWrite.ReadLockMode` is changed PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: include cache updates and routing hint into BeginTransaction and Commit request/response respectively PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `params` in message `.google.spanner.v1.PartitionQueryRequest` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: include cache updates into the ResultSet response PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `transaction_tag` in message `.google.spanner.v1.RequestOptions` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `param_types` in message `.google.spanner.v1.PartitionQueryRequest` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `commit_timestamp` in message `.google.spanner.v1.BatchWriteResponse` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT chore: adjust initial_poll_delay for CreateDatabase and UpdateDatabaseDdl LRO operations PiperOrigin-RevId: 853884590 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@136a2c43](googleapis/googleapis@136a2c43) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add a ClientContext field to Spanner requests PiperOrigin-RevId: 853323071 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@211d22fa](googleapis/googleapis@211d22fa) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add Secure Parameters to the ClientContext PiperOrigin-RevId: 853323071 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@211d22fa](googleapis/googleapis@211d22fa) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: Exposing total CPU related fields in AutoscalingConfig PiperOrigin-RevId: 845819318 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@6e20492a](googleapis/googleapis@6e20492a) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: Update high_priority_cpu_utilization_percent in AutoscalingConfig to be Optional and clarify its behavior when not specified PiperOrigin-RevId: 845819318 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@6e20492a](googleapis/googleapis@6e20492a) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: minor update for Spanner Location API PiperOrigin-RevId: 834841888 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@ded7ed1e](googleapis/googleapis@ded7ed1e) END_NESTED_COMMIT END_COMMIT This pull request is generated with proto changes between [googleapis/googleapis@a17b84ad](googleapis/googleapis@a17b84a) (exclusive) and [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602d) (inclusive). Librarian Version: v1.0.2-0.20260309131826-42ac5c451239 Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:b8058df4c45e9a6e07f6b4d65b458d0d059241dd34c814f151c8bf6b89211209 Fixes #1527 This PR also moves `ClientContext` under `RequestOptions` as per #1527 (comment). `ClientContext` was added in #1499 but the feature has not been released yet so it is safe to move.

PR created by the Librarian CLI to generate Cloud Client Libraries code from protos. BEGIN_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `routing_hint` in messages `.google.spanner.v1.ResultSet` and `.google.spanner.v1.PartialResultSet` are changed PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment in message `.google.spanner.v1.TransactionOptions.ReadWrite.ReadLockMode` is changed PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: include cache updates and routing hint into BeginTransaction and Commit request/response respectively PiperOrigin-RevId: 878019893 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602db) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `params` in message `.google.spanner.v1.PartitionQueryRequest` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: include cache updates into the ResultSet response PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `transaction_tag` in message `.google.spanner.v1.RequestOptions` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `param_types` in message `.google.spanner.v1.PartitionQueryRequest` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: A comment for field `commit_timestamp` in message `.google.spanner.v1.BatchWriteResponse` is changed PiperOrigin-RevId: 865546011 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@8d30990f](googleapis/googleapis@8d30990f) END_NESTED_COMMIT BEGIN_NESTED_COMMIT chore: adjust initial_poll_delay for CreateDatabase and UpdateDatabaseDdl LRO operations PiperOrigin-RevId: 853884590 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@136a2c43](googleapis/googleapis@136a2c43) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add a ClientContext field to Spanner requests PiperOrigin-RevId: 853323071 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@211d22fa](googleapis/googleapis@211d22fa) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add Secure Parameters to the ClientContext PiperOrigin-RevId: 853323071 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@211d22fa](googleapis/googleapis@211d22fa) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: Exposing total CPU related fields in AutoscalingConfig PiperOrigin-RevId: 845819318 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@6e20492a](googleapis/googleapis@6e20492a) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: Update high_priority_cpu_utilization_percent in AutoscalingConfig to be Optional and clarify its behavior when not specified PiperOrigin-RevId: 845819318 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@6e20492a](googleapis/googleapis@6e20492a) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: minor update for Spanner Location API PiperOrigin-RevId: 834841888 Library-IDs: google-cloud-spanner Source-link: [googleapis/googleapis@ded7ed1e](googleapis/googleapis@ded7ed1e) END_NESTED_COMMIT END_COMMIT This pull request is generated with proto changes between [googleapis/googleapis@a17b84ad](googleapis/googleapis@a17b84a) (exclusive) and [googleapis/googleapis@5c9602db](googleapis/googleapis@5c9602d) (inclusive). Librarian Version: v1.0.2-0.20260309131826-42ac5c451239 Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:b8058df4c45e9a6e07f6b4d65b458d0d059241dd34c814f151c8bf6b89211209 Fixes googleapis/python-spanner#1527 This PR also moves `ClientContext` under `RequestOptions` as per googleapis/python-spanner#1527 (comment). `ClientContext` was added in googleapis/python-spanner#1499 but the feature has not been released yet so it is safe to move.

aseering and others added 8 commits February 11, 2026 20:18

Merge branch 'main' into feat/client-context-support

55b213b

Merge remote-tracking branch 'origin/main' into feat/client-context-s…

aca8616

…upport

chore: remove unused code

5fe5319

Move race-condition fix to a separate branch

c301cbc

aseering requested review from a team as code owners February 24, 2026 18:01

product-auto-label bot added the size: l Pull request size is large. label Feb 24, 2026

blunderbuss-gcf bot assigned rahul2393 Feb 24, 2026

product-auto-label bot added the api: spanner Issues related to the googleapis/python-spanner API. label Feb 24, 2026

gemini-code-assist bot reviewed Feb 24, 2026

View reviewed changes

olavloite and others added 4 commits February 25, 2026 15:31

test: remove thread-unsafe assertions for concurrent tests

424223d

chore: move ClientContext validation to a helper function

35dba42

Merge remote-tracking branch 'remote/main' into feat/client-context-s…

95a9549

…upport

fix: remove unused ClientContext imports to pass flake8 lint

2ffcdf4

olavloite approved these changes Mar 3, 2026

View reviewed changes

olavloite merged commit 9fcb647 into googleapis:main Mar 3, 2026
24 of 28 checks passed

ohmayr mentioned this pull request Mar 24, 2026

chore: librarian release pull request: 20260324T002237Z #1519

Closed

This was referenced Mar 25, 2026

Move ClientContext under RequestOptions #1527

Closed

chore: librarian generate pull request: 20260325T173440Z #1529

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(spanner): add Client Context support to options#1499

feat(spanner): add Client Context support to options#1499
olavloite merged 12 commits intogoogleapis:mainfrom
aseering:feat/client-context-support

aseering commented Feb 24, 2026

Uh oh!

gemini-code-assist bot commented Feb 24, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 24, 2026

Uh oh!

chalmerlowe commented Mar 2, 2026

Uh oh!

olavloite commented Mar 3, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

aseering commented Feb 24, 2026

Uh oh!

gemini-code-assist bot commented Feb 24, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

chalmerlowe commented Mar 2, 2026

Uh oh!

olavloite commented Mar 3, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants